Managing messaging services

ABSTRACT

In some implementations, messaging services, through which messages from an entity, such as a company, are communicated to various users, are managed. In one aspect, the techniques described may be provided by a messaging management service that keeps track of such messaging services and provides messages to users through these messaging services on behalf of various companies. In this way, the messaging management service may enable companies to quickly establish a presence on new communication platforms and more easily communicate through the mobile communication and social networking services that are most suitable to their existing and potential customers.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a divisional of U.S. application Ser. No.14/947,138, filed Nov. 20, 2015, now allowed, which is incorporated byreference in its entirety.

TECHNICAL FIELD

This disclosure generally relates to messaging services.

BACKGROUND

In recent years, mobile devices and social networks have changed the waythat people communicate and interact with one another. As such, manycompanies have started to utilize mobile communication and socialnetworking services as channels for communicating with existing andpotential customers. With new services being regularly released andexisting services regularly losing popularity amongst users, this sceneis, however, in a constant state of change. As a result, it has becomeincreasingly more difficult for companies to keep abreast of the mobilecommunication and social networking services being used by existing andpotential customers at any given time.

SUMMARY

In general, an aspect of the subject matter described in thisspecification may involve a process for managing the messaging servicesthrough which messages from an entity, such as a company, arecommunicated to various users. This capability may be provided by amessaging management service that keeps track of such messaging servicesand provides messages to users through these messaging services onbehalf of various companies. In this way, the messaging managementservice may enable companies to quickly establish a presence on newcommunication platforms and more easily communicate through the mobilecommunication and social networking services that are most suitable totheir existing and potential customers.

In some aspects, the subject matter described in this specification maybe embodied in methods that may include the actions of accessing, by amessaging management service, message recipient information thatincludes, for each of multiple message recipients, (i) preference dataidentifying one or more messaging services through which messages are tobe sent to a user, and, (ii) for each of the messaging services throughwhich messages are to be sent to the user, account information for theuser, and receiving, by the messaging management service and from amessage initiator, a request to transmit a message, where the requestincludes at least (i) a message content type identifier that indicates atype of message that is to be transmitted, and (ii) data identifying oneor more message recipients. Such methods that may further include theactions of, for each message recipient, selecting, by the messagingmanagement service, one or more particular messaging services based onthe preference data for the message recipient, and, for each of theparticular messaging services, generating, by the messaging managementservice, a message based on the message content type identifier,transmitting, by the messaging management service, the message and theaccount information for the user to the messaging service, and inresponse to transmitting the message, receiving, by the messagingmanagement service, an acknowledgement from the messaging service. Suchmethods that may further include the actions of generating, by themessaging management service, a response to the request based on atleast one of the one or more acknowledgements, and transmitting, by themessaging management service and to the message initiator, the responseto the request.

Other implementations of this and other aspects include correspondingsystems, apparatus, and computer programs, configured to perform theactions of the methods, encoded on computer storage devices. A system ofone or more computers can be so configured by virtue of software,firmware, hardware, or a combination of them installed on the systemthat in operation cause the system to perform the actions. One or morecomputer programs can be so configured by virtue of having instructionsthat, when executed by data processing apparatus, cause the apparatus toperform the actions.

These other versions may each optionally include one or more of thefollowing features. For instance, implementations may include the one ormore particular messaging services including one or more socialnetworking services. In some implementations, the request may furtherinclude (iii) a set of content that is to be included in the messagethat is to be transmitted. In these implementations, generating themessage based on the message content type identifier may, for instance,include selecting, from among multiple templates that are eachassociated with different message content type identifiers, a particulartemplate that is associated with the received message content typeidentifier, and populating the particular template with the set ofcontent. In addition, the multiple templates may, in some examples, bemaintained by one or more administrators associated with the messageinitiator.

In some implementations, the preference data may further identify alanguage in which messages are to be provided to the user. In someexamples, receiving, by the messaging management service and from themessage initiator, the request to transmit the message may, forinstance, include receiving, by the messaging management service andfrom the message initiator, a request (i) under a simple object accessprotocol and (ii) to transmit a message.

In some examples, accessing, by the messaging management service,message recipient information may include accessing, by the messagingmanagement service, message recipient information for each of multipleusers that are registered to receive messages on behalf of the messageinitiator. In such implementations, at least a portion of the messagerecipient information for each of the multiple users may, for instance,be obtained in through one or more processes through which each user isregistered to receive messages on behalf of the message initiator. Inone aspect, the one or more processes through which each user isregistered to receive messages on behalf of the message initiator areperformed, at least in part, by one or more computing devices that hosta website associated with the message initiator.

In some implementations, selecting one or more particular messagingservices based on the preference data for the message recipient mayinclude, for each of one or more message recipients, selecting, by themessaging management service, two or more particular messaging servicesbased on the preference data for the message recipient. In suchimplementations, generating the message based on the message contenttype identifier may include, for each of the two or more particularmessaging services, generating, by the messaging management service, amessage based on the message content type identifier that is formattedfor the respective one of the two or more particular messaging services.

In some examples, generating the message based on the message contenttype identifier may include selecting, from among multiple templatesthat are each associated with different message content type identifiersand maintained by one or more administrators through a webadministration console of the messaging management service, a particulartemplate that is associated with the received message content typeidentifier, and populating the particular template with the set ofcontent. The web administration console of the messaging managementservice may, in some instances, enable templates to be added andmodified by the one or more administrators.

In some aspects, the subject matter described in this specification maybe embodied in methods that may include the actions of accessing, by amessaging management service, message recipient information thatincludes, for each of multiple message recipients, (i) preference dataidentifying one or more existing messaging services through whichmessages are to be sent to a user, and, (ii) for each of the existingmessaging services through which messages are to be sent to the user,account information for the user, receiving, by the messaging managementservice, new messaging service provisioning information for a newmessaging service, where the new messaging service provisioninginformation includes (i) information that associates message contenttype identifiers to message templates that are formatted for themessaging service, and (ii) instructions for electronicallycommunicating messages to the new messaging service, transmitting, bythe messaging management service and to one or more message initiators,a notification indicating that messages may now be transmitted throughthe new messaging service, and receiving, by the messaging managementservice and from one or more of the message initiators, updated messagerecipient information that includes, for each of one or more of themultiple message recipients, (i) updated preference data identifying thenew messaging service, and, (ii) account information for the newmessaging service and the user.

Other implementations of this and other aspects include correspondingsystems, apparatus, and computer programs, configured to perform theactions of the methods, encoded on computer storage devices. A system ofone or more computers can be so configured by virtue of software,firmware, hardware, or a combination of them installed on the systemthat in operation cause the system to perform the actions. One or morecomputer programs can be so configured by virtue of having instructionsthat, when executed by data processing apparatus, cause the apparatus toperform the actions.

These other versions may each optionally include one or more of thefollowing features. For instance, receiving, by the messaging managementservice and from one or more of the message initiators, updated messagerecipient information may, in some implementations, include receiving,by the messaging management service and from one or more of the messageinitiators, updated message recipient information based on an indicationthat the user would like receive messages through the new messagingservice. In some examples, the indication that the user would likereceive messages through the new messaging service is received by themessage initiator through a website associated with the messageinitiator.

In some implementations, such methods that may further include theactions of receiving, by the messaging management service, one or moreupdates to enable the messaging management service to generate messagesthat are compatible with the new messaging service. In some examples,such methods that may further include the actions of updating themessage recipient information for each of the one or more of themultiple message recipients, to reflect the (i) updated preference dataidentifying the new messaging service, and, (ii) account information forthe new messaging service and the user.

In some aspects, the subject matter described in this specification maybe embodied in methods that may include the actions of receiving, by amessage initiator, an indication that a particular message recipient hasinitiated communication of a message through a particular messagingservice, determining, by the message initiator, that message recipientinformation for the particular message recipient indicates that messagesare not to be transmitted to the particular message recipient throughthe particular messaging service, in response to determining that themessage recipient information for the particular message recipientindicates that the messages are not to be sent to the particular messagerecipient through the particular messaging service, providing, by themessage initiator, a prompt for the particular message recipient toconfirm that the message is to be transmitted through the particularmessaging service, receiving, by the message initiator, a response fromthe particular message recipient confirming that the message is to betransmitted through the particular messaging service, and in response toreceiving the response from the particular message recipient confirmingthat the message is to be transmitted through the particular messagingservice, transmitting, to a messaging management service, a request totransmit a message, where the request includes at least (i) a messagecontent type identifier that indicates a type of the message that is tobe transmitted, (ii) data identifying the particular message recipient,and (iii) data indicating that the particular message recipient hasoverridden preference data indicating that messages are not to betransmitted to the particular message recipient through the particularmessaging service.

Other implementations of this and other aspects include correspondingsystems, apparatus, and computer programs, configured to perform theactions of the methods, encoded on computer storage devices. A system ofone or more computers can be so configured by virtue of software,firmware, hardware, or a combination of them installed on the systemthat in operation cause the system to perform the actions. One or morecomputer programs can be so configured by virtue of having instructionsthat, when executed by data processing apparatus, cause the apparatus toperform the actions.

These other versions may each optionally include one or more of thefollowing features. For instance, providing, by the message initiator,the prompt for the particular message recipient to confirm that themessage is to be transmitted through the particular messaging servicemay, in some implementations, include providing, by the messageinitiator and through an interface of a website associated with themessage initiator, a prompt for the particular message recipient toconfirm that the message is to be transmitted through the particularmessaging service. In these implementations, receiving, by the messageinitiator, the response from the particular message recipient confirmingthat the message is to be transmitted through the particular messagingservice may include receiving, by the message initiator and through theinterface of the website associated with the message initiator, aresponse from the particular message recipient confirming that themessage is to be transmitted through the particular messaging service.In some examples, the particular messaging service is a socialnetworking service. In addition, the request may, in some examples,further include (iv) a set of content that is to be included in themessage that is to be transmitted.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other potential features, aspects, and advantages ofthe subject matter will become apparent from the description, thedrawings, and the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1A-B are conceptual diagrams of an exemplary framework formanaging messages on behalf of one or more message initiators.

FIG. 2 illustrates an example of a sequence in which a messaging serviceis provisioned as a service through which messages are sent torecipients on behalf of one or more message initiators.

FIG. 3 illustrates an example of a sequence in which one or moremessaging preferences are overridden.

FIG. 4 is a flow chart of an example process for managing messages onbehalf of one or more message initiators.

FIG. 5 is a diagram of exemplary computing devices.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a conceptual diagram of an exemplary framework for managingmessages on behalf of one or more message initiators in a system 100.More particularly, the diagram depicts a client device 102, a messageinitiator 104, a messaging management service 120, and messagingservices 130 that collectively make up system 100. The diagram alsodepicts exemplary data that is communicated within system 100 intime-sequenced stages “A” to “E,” respectively. Briefly, and asdescribed in further detail below, the client device 102 may receivemessages through messaging services 130 that are sent by the messagingmanagement service 120 on behalf of the message initiator 104.

The client device 102, message initiator 104, messaging managementservice 120, and messaging services 130 may communicate with one anotherover network 110, and may each be implemented using, for example, one ormore general-purpose computers capable of responding to and executinginstructions in a defined manner, personal computers, special-purposecomputers, workstations, servers, or mobile devices. The system 100 mayinclude multiple message initiators, but may be described with referenceto message initiator 104 for exemplary purposes. Similarly, the system100 may include multiple client devices, but may be described withreference to client device 102 exemplary purposes.

In this example, the message initiator 104 may include one or morecomputing devices that are associated with one or more subscribers ofthe messaging management service 120. A subscriber may, for instance,correspond to a company, a group, and/or an individual that leveragesthe messaging management service 120 to communicate with customers,group members, and the like. A user of client device 102 may, forinstance, receive messages provided by the messaging management service120 on behalf of subscribing companies and/or groups of which the userof client device 102 is a customer or member.

The messaging services 130 may include communication and socialnetworking services for which the user of client device 102 holds anaccount. The messaging services 130 may, for example, include socialnetworking services, e-mail services, image sharing services, SMS orother text-messaging services, mobile chat services, video conferencingservices, and the like. In some examples, the user of client device 102may register with a company or group that subscribes to the messagingmanagement service 120 to receive messages through such messagingservices 130. For instance, the user of client device 102 may sign up toreceive these messages through a company's website. Information such asuser preferences and messaging account details may be provided to thecompany by the user of client device 102 in this registration process.This information may be received by or otherwise made accessible to themessage initiator 104 and stored in a preferences and contact detailsdatabase 105. In addition, the message initiator 104 may pass some orall of this information along to messaging management service 120, whichmay in turn store such information in a preferences and contact detailsdatabase 125. In implementations in which registration is performedthrough use of a website, the message initiator 104 may include oroperate in cooperation with one or more servers hosting the website.

The messaging management service 120 may include a validation engine122, a messaging service provisioner 124, and a message generator 126.The functionality of each module included in the messaging managementservice 120 is described in more detail below. The messaging managementservice 120 may further include a web administration console throughwhich subscribers may interact with the messaging management service 120to define the types of messages that may be sent to users. Variousmessage templates of the subscriber's specifications may be stored in atemplate inventory 123 and later accessed by the messaging managementservice 120 to generate messages in response to a subscriber's requests.The messaging management service 120 may further transmit thesegenerated messages to a particular subset of messaging services 130 fordeliver to an end user. In addition, the messaging management service120 may leverage messaging service provisioner 124 to provision each ofthe messaging services 130 for use as channels through which subscribersof the messaging management service 120 may communicate with end users.

The user of client device 102 may sign up to be provided with messages,such as reminders and other notifications, in response to satisfactionof one or more conditions. For example, the user of client device 102may wish to be provided with a reminder message fourteen days prior tothe expiration of their contract with the company. In another example,the user of client device 102 may wish to be provided with anotification when the stock of a particular product sold by the companyis replenished. These conditions may be indicated by informationincluded in the preferences and contact details 105 and monitored by themessage initiator 104.

In stage A, the message initiator 104 may send a message request 117 tothe messaging service 120. Message request 117 may, for example, be sentin response to the satisfaction of one or more conditions that are beingmonitored by the message initiator 104. For example, the messageinitiator 104 may, in stage A, determine that a contract between thecompany and the user of client device 102 is set to expire in fourteendays, based at least on information stored in the preferences andcontact details database 105. In particular, the message request 117 mayinclude a message content type identifier that indicates a type ofmessage that is to be transmitted and data identifying one or moremessage recipients. A content type identifier may correspond to one ormore message templates as defined by one or more subscribers of themessaging management service 120 that are associated with messageinitiator 104. In the example of FIG. 1A, the type of message that is tobe transmitted as indicated by the content type identifier included inthe message request 117 may correspond to a reminder about expiration ofa contract. Similarly, the data identifying one or more messagerecipients that is included in the message request 117 may, in thisexample, identify the user of client device 102 as a message recipient.

In some implementations, the messaging management service 120 mayleverage the validation engine 122 to perform one or more validationprocesses upon the message request 117. Such validation processes may,for example, include those which conform to a simple object accessprotocol (“SOAP”). The messaging management service 120 may provideresults output by the validation engine 122 to message initiator 117upon completion of such validation processes. In some implementations,the messaging management service 120 may not perform the processesdescribed below unless message request 117 is successfully validated bythe validation engine 122.

After receiving message request 117, the messaging management service120 may utilize the data identifying the user of client device 102, asincluded in the message request 117, to retrieve information associatedwith the user of client device 102 that is stored in preferences andcontact details database 125. Such information may include preferencedata identifying one or more of messaging services 130 through whichmessages are to be sent to the user of client device 102 and, for eachof these one or more messaging services 130, account information for theuser of client device 102. That is, the messaging management service 120may determine which of messaging services 130 are to be utilized toreach the user of client device 102, as well as the details of theaccounts that the user of client device 102 holds with each of thesemessaging services 130. In this way, the message initiator 104 may notneed to directly include information about which messaging services touse in the message request 117 that it transmits to the messagingmanagement service 120. It can be noted that, by performing suchinformation retrieval processes, the messaging management service 120allows the message initiator 104 to perform relatively little work tobroadcast messages to its users.

For example, the user of client device 102 may have signed up toreminders about expiration of their contract with the company associatedwith message initiator 104 through a social network service, an e-mailservice, and an image sharing service. In this example, the messagingmanagement service 120 may identify the particular social networkservice, e-mail service, and image sharing service from among themessaging services 130, and further identify account information foreach of these services that corresponds to the user of the client device102.

In addition, the messaging management service 120 may utilize themessage content type identifier that indicates the type of message thatis to be transmitted, as included in the message request 117, toretrieve a message template from the template inventory 123 for eachrespective one of the messaging services 130 that are determined to beutilized to reach the user of client device 102. Each message templateincluded in the template inventory 123 may be stored in association witha message content type identifier and data identifying the particularone of messaging services 130 for which the respective message isformatted. It can be seen that the information included in the messagerequest 117 and preferences and contact details 125 may enable themessaging management service 120 to identify and retrieve messagetemplates from the template inventory 123 of an appropriate type andformat. In the example mentioned above, the messaging management service120 may retrieve contract expiration reminder templates from thetemplate inventory 123 that are formatted for the particular socialnetwork service, e-mail service, and image sharing service identified bythe messaging management service 120 for the user of client device 102.

Upon retrieving the appropriate message templates in response toreceiving message request 117, the messaging management service 120 mayleverage message generator 126 to generate a message based on each ofthe retrieved message templates. The message generator 126 may include adedicated sub-module for each one of messaging services 130 thatgenerates messages formatted for the respective messaging service. Insome examples, these sub-modules may be invoked by the messagingmanagement services 120 in a dynamic manner using Java reflection. Insome examples, the message generator 126 may generate messages bypopulating each retrieved message template with content or otherwisegenerating a message including such content based on each retrievedmessage template to include additional information. The messagingmanagement service 120 may, for example, obtain such content based oninformation included in the message request 117, preferences and contactdetails database 125, template inventory 123, or a combination thereof.

In stage B, the messaging management service 120 may transmit eachmessage 127 that is has generated, along account information 129 thatcorresponds to the user of the client device 102 to each identified oneof messaging services 130. FIG. 1B is a conceptual diagram of anexemplary framework for managing messages on behalf of one or moremessage initiators in a system 100B. The system 100B may, for example,represent system 100 as described in association with FIG. 1A or aportion thereof. In the example of FIG. 1B, a user 103 may correspond tothe user of client device 102, and a social networking service 130 a, ane-mail service 130 b, and an image sharing service 130 c may correspondto the subset of messaging services 130 through which user 103 desiresto receive reminders about expiration of their contract with a company,“exampleCorp” that subscribes to the messaging management service 120and is associated with message initiator 104.

Referring now to FIG. 1B, it can be seen that, in stage B, the socialnetwork service 130 a, e-mail service 130 b, and image sharing service130 c are provided with messages 127 a, 127 b, and 127 a and accountinformation 129 a, 129 b, and 129 a, respectively. Such messages 127 a-cand account information 129 a-c may correspond to that which istransmitted by messaging management service 120 in stage B. In thisexample, messages 127 a, 127 b, and 128 c may have been generated bysub-modules included in the message generator 126 dedicated to thesocial networking service 130 a, the e-mail service 130 b, and the imagesharing service 130 c, respectively. In some implementations, theaccount information 129 provided to each messaging service may furtherinclude details of one or more accounts held by the one or moresubscribers associated with the message initiator 104.

In some examples, the contents of messages 127 a-c and accountinformation 129 a-c may cause each messaging service to send, post, orotherwise make each generated message to available to user 103. In stageC, messages generated and sent by messaging management service 120 onbehalf of exampleCorp may be provided to user 103. For example, themessage 127 a and account information 129 a provided to the socialnetwork service 130 a by the messaging management service 120 may causethe social network service 130 a to post a message on behalf ofexampleCorp to the wall of an account associated with user 103. The user103 may then be able to view this wall post by accessing the socialnetworking service 130 a through a web browser or an application runningon the client device 102, one or more other computing devices, or acombination thereof. For instance, the client device 102 may displayscreen 131 a when the user 103 accesses the wall associated with theiraccount for social networking service 130 a. By further includingdetails of exampleCorp's account for social networking service 130 a,the message posted on the wall of user 103 may appear to have been sentby exampleCorp.

The message shown within display screen 131 a may reflect the messagegenerated by message generator 126 using a message template stored intemplate inventory 123 for a contract expiration reminder formatted forthe social networking service 130 a. Such a message template may, forexample, have been defined by one or more users associated withexampleCorp through the web administration console of the messagingmanagement service 120 and may correspond to the content type identifierincluded in the message request 117. More particularly, this message mayreflect that which was generated by the sub-module included in messagegenerator 126 that corresponds to the social networking service 130 a.The resulting message posted on the wall of user 103 may, for instance,include text that says “Hi Mike, just reminding you that your contractwith exampleCorp expires at the end of this month.”

In this instance, the message template may have been that of a wallposting that includes strings of characters and variable objects thatare to be replaced with content that is relevant to user 103,exampleCorp, one or more conditions whose satisfaction triggered messagerequest 117, or a combination thereof. For example, portions of themessage posted on the wall of user 103 such as (i) “Mike,” (ii)“exampleCorp,” and (iii) “at the end of this month” may representcontent that was used to replace three different variable objects in themessage template for a contract expiration reminder formatted for thesocial networking service 130 a that serve as placeholders for (I) thename of user to which the message is being sent, (II) the name of theentity that has requested that the message be sent, and (III) the dateon which the user's contract expires. The dedicated sub-module includedin message generator 126 that corresponds to the social networkingservice 130 a may perform one or more operations to identify and obtainthe content that is appropriate for each message. In someimplementations, such content may be associated with informationincluded in message request 117. In these implementations, the messagingmanagement service 120 may obtain content from one or more webresources, databases, or other computing devices on the basis ofinformation included in message request 117. In other implementations,such content may be included in message request 117.

In another example, the message 127 b and account information 129 bprovided to the e-mail service 130 b by the messaging management service120 may cause an e-mail to be sent to the e-mail account of user 103 onbehalf of exampleCorp to the wall of an account associated with user103. The user 103 may then be able to view this e-mail message byaccessing the e-mail service 130 b through a web browser or anapplication running on the client device 102, one or more othercomputing devices, or a combination thereof. For instance, the clientdevice 102 may display screen 131 b when the user 103 accesses theiraccount for the e-mail service 130 b. By further including details ofexampleCorp's e-mail account, the message e-mailed to user 103 mayappear to have been sent by exampleCorp.

The message shown within display screen 131 b may reflect the messagegenerated by message generator 126 using a message template stored intemplate inventory 123 for a contract expiration reminder formatted forthe e-mail service 130 b. Such a message template may, for example, havebeen defined by one or more users associated with exampleCorp throughthe web administration console of the messaging management service 120.Like the message template described above in reference to display screen131 a, this message template may also correspond to the content typeidentifier included in the message request 117. More particularly, thismessage may reflect that which was generated by the sub-module includedin message generator 126 that corresponds to the e-mail service 130 b.The resulting e-mail message sent to user 103 may, for instance, includetext that says “Hi Mike,” “We just wanted to remind you that yourcontract expires at the end of this month,” “Click here to renew yourcontract or sign up for another one of our great offers,” and may besigned “exampleCorp.”

In this instance, the message template may have been that of an emailthat includes strings of characters and variable objects that are to bereplaced with content that is relevant to user 103, exampleCorp, one ormore conditions whose satisfaction triggered message request 117, or acombination thereof. Portions of this e-mail message may be identifiedand obtained in a manner similar to that which has been described abovein association with display screen 131 a. In addition, the dedicatedsub-module included in message generator 126 that corresponds to thee-mail service 130 b may perform one or more operations to augment the“Click here” text with a particular hyperlink. In this example, themessage generated by messaging management service 120 may link the“Click here” text to a particular page of exampleCorp's website. Theuniform resource locator (“URL”) for this page may be identified andobtained using one or more of the techniques described above.

In yet another example, the message 127 c and account information 129 cprovided to the image sharing service 130 c by the messaging managementservice 120 may cause the image sharing service 130 c to share an imageconveying a message on behalf of exampleCorp with an account associatedwith user 103. The user 103 may then be able to view the image that hasbeen shared with them by accessing the image sharing service 130 cthrough a web browser or an application running on the client device102, one or more other computing devices, or a combination thereof. Forinstance, the client device 102 may display screen 131 c when the user103 accesses their account for image sharing service 130 c. By furtherincluding details of exampleCorp's account for image sharing service 130c, it may appear as though exampleCorp has shared the image with user103.

The image shown within display screen 131 c may reflect the messagegenerated by message generator 126 using a message template stored intemplate inventory 123 for a contract expiration reminder formatted forthe image sharing service 130 c. Such a message template may, forexample, have been defined by one or more users associated withexampleCorp through the web administration console of the messagingmanagement service 120. Like the message template described above inreference to display screens 131 a and 131 b, this message template mayalso correspond to the content type identifier included in the messagerequest 117. More particularly, this image may reflect a messagegenerated by the sub-module included in message generator 126 thatcorresponds to the image sharing service 130 c. The resulting imageshared with user 103 may, for instance, include graphics of text thatsay “contract's almost up,” “Renew your contract today and save 20%,”and “exampleCorp,” “save more.” In addition, the image shared with user103 may further include other non-textual graphics such as emoticons andother icons.

In this instance, the message template may have been that of an imagethat includes graphics and variable graphical objects that are to bereplaced with graphics that are relevant to user 103, exampleCorp, oneor more conditions whose satisfaction triggered message request 117, ora combination thereof. Graphics included in this message may beidentified and obtained in a manner similar to that which has beendescribed above in association with display screens 131 a and 131 b.

Each of the messaging services may provide the messaging managementservice 120 with acknowledgement of the respective message having beensuccessfully received by the messaging service and/or provided for user103. In the event that the respective message is not successfullyreceived by the messaging service and/or provided for user 103, eachmessaging service may instead provide the messaging management service120 with a negative-acknowledgement. Referring again to FIG. 1A, it canbe seen that such acknowledgements are provided to the messagingmanagement service 120 by messaging services 130 in stage D. Themessaging management service 120 may, in turn, provide data indicatingsuch acknowledgements to the message initiator in stage E. Theseacknowledgement and negative-acknowledgement messages may serve to alertmessaging management service 120 and/or message initiator 104 to anyerrors that might have occurred in providing messages. In some examples,one or more computing devices of system 100 may take corrective measuresin the presence of negative-acknowledgement messages to resolveoutstanding issues and again attempt to successfully provide messages.

In some implementations, the client device 102 may include a mobilecomputing device, personal digital assistant, cellular telephone,smart-phone, tablet, laptop, desktop, workstation, and other computingdevices. The client device 102 accesses the network 110 using a wirelessconnection, such as a cellular telephone data connection, a Wi-Ficonnection, or other wireless connection that can be used for sendingdata to and receiving data from message initiator 104 and messagingservices 130. In addition, the message initiator 104, messagingmanagement service 120, and/or messaging services 130 may rely upon oneor more remotely-located devices such as servers, databases, and/orcloud computing devices to perform at least a portion of its functionsas described herein.

In some implementations, the network 110 includes one or more networks,such as a local area network, a wide area network, and/or the Internet.One or more of the networks in the network 110 may be wireless, such asa cellular telephone network or a Wi-Fi network.

FIG. 2 illustrates an example of a sequence 200 in which a messagingservice is provisioned as a service through which messages are sent torecipients on behalf of one or more message initiators. The followingdescribes the processes of sequence 200 as being performed by componentsof systems that are described with reference to FIGS. 1A-B. However, theprocesses of sequence 200 may be performed by other systems or systemconfigurations. At 202, the messaging management service 120 receivesprovisioning information for a new messaging service. For example, themessaging management service 120 may be provided with a new sub-modulethat generates messages to be transmitted through a new messagingservice. This may, for instance, be a mobile communication or socialnetworking service that was recently released or gained popularity. Themessaging service provisioner 124 may, for instance, perform some or allof the operations described herein in association with provisioning thenew messaging service.

The messaging management service 120 may, at 202, receive new messageprovisioning information that associates message content typeidentifiers to message templates that are formatted for the newmessaging service and instructions for electronically communicatingmessages to the new messaging service. Following the example providedabove in reference to FIGS. 1A-B, this information may, for instance,include that which associates the content type identifier for a contractexpiration reminder with a particular message template that thisformatted for the new messaging service. One or more message templatesformatted for the new messaging service may be added to templateinventory 125 in conjunction with the new messaging service provisioninginformation being received by the messaging management service 120. Insome implementations, the new messaging service provisioninginformation, sub-module, and message templates may be provided to themessaging management service 120 by one or more administrators of themessaging management service 120.

At 204, the messaging management service 120 may transmit a notificationto one or more message initiators 104 which indicates that messages maynow be transmitted through the new messaging service. In this way, themessaging management service 120 may inform its subscribers of thenewly-supported messaging service through which they may be able tocommunicate with end users. In some examples, the channel through whichthe messaging management service 120 and message initiator 104communicate may be predetermined. In response to receiving thisnotification, each message initiator 104 may, at 206, request that eachuser that is registered to receive their messages confirm that they wishto also receive messages through the new messaging service. Suchrequests may, for instance, be provided to users through a websiteassociated with each message initiator 104.

For instance, the client device 102 may display screen 207 a when aregistered user accesses a website associated with the correspondingmessage initiator 104. As shown within display screen 207 a, the websiteassociated with the corresponding message initiator 104 may prompt theuser of client device 102 to indicate whether they would like to receivemessages through the new messaging service supported by messagingmanagement service 120. The client device 102 may, for example, displayscreen 207 b when the registered user indicates whether they would liketo receive messages through the new messaging service in response to theprompt.

At 208, the client device 102 may provide confirmation of whether theuser of client device 102 wishes to receive messages through the newmessaging service to messaging initiator 104. This may, for instance,occur upon submission of user indication to the website associated withthe corresponding message initiator 104, as shown within display screen207 b. At 210, the message initiator 104 may provide recipientinformation to the messaging management service 120. Such recipientinformation may include updated recipient information for each of one ormore of multiple message recipients. In the example of FIG. 2, this mayat least include updated recipient information for the user of clientdevice 102. Furthermore, the updated recipient information may includeupdated preference data identifying the new messaging service andaccount information for the new messaging service and the user. Althoughnot shown in FIG. 2, the user of client device 120 may provide theirpreferences for receiving messages through the new messaging servicedetails of an account held by the user of client device 120 with the newmessaging service. This information may also be received through thewebsite associated with the corresponding message initiator 104. Uponreceiving the updated recipient information at 210, the messagingmanagement service 120 may update the information maintained in thepreferences and contact details database 125 for each registered userthat has signed up to receive messages through the new messagingservice.

In some implementations, the initial registration process that occursbetween users and message initiators 104 may include processes that aresimilar to at least a portion of the processes of sequence 200. Forinstance, each user may provide their messaging preferences through awebsite associated with a message initiator 104 in a process similar tothat which has been described above in reference to sequence 200 at 206and 208. The preferences provided by each user may, for example,indicate the particular subset of messaging services through which therespective user wishes to receive messages, the language in whichmessages provided through each messaging service are to be written,dates and times at which the user wishes to be provided with messages,the types of messages that are to be provided through each messagingservice, the conditions under which each type of message is to beprovided through each messaging service, and the like. The accountinformation provided by each user may, for example, indicate a usernameof the respective user for each messaging service and other informationthat indicates an address at which the respective user can be reachedthrough each messaging service. For example, such other information mayinclude an e-mail address, phone number, and/or geographical locationassociated with the respective user. Upon receiving the informationdescribed above in the registration process, the message initiator 104may store such information in the preferences and contact detailsdatabase 105. Similarly, the messaging management service 120 may storethis information in the preferences and contact details database 105upon receiving such information from the message initiator 104 in aprocess similar to that which has been described above in reference tosequence 200 at 210.

FIG. 3 illustrates an example of a sequence 300 in which one or moremessaging preferences are overridden. The following describes theprocesses of sequence 300 as being performed by components of systemsthat are described with reference to FIGS. 1A-B. However, the processesof sequence 300 may be performed by other systems or systemconfigurations. At 302, the client device 102 may provide an indicationthat the user of client device 102 has initiated communication of amessage through a particular messaging service. This may, for instance,be received by the message initiator 104 through an associated website.For instance, the user of client device 102 may order a product off ofthe website associated with message initiator 104 and indicate that theywish to be provided with a confirmation message for this purchasethrough a particular messaging service. The message initiator 104 maydetermine that existing message recipient information for the user ofclient device 102 indicates that messages are not to be transmitted tothe user of client device 102 through the particular messaging service.For example, the message initiator 104 may reference existinginformation for the user of client device 102 that is stored in thepreferences and contact details database 105 and determine that, in aprevious registration process, the user of client device 102 explicitlyindicated that they did not wish to receive messages through theparticular messaging service.

At 304, the message initiator 104 may request that the user of clientdevice 102 confirm that they wish to override their default preferencesin order to receive the confirmation message through the particularmessaging service. For instance, the client device 102 may displayscreen 305 a as provided by the website associated with the messageinitiator 104 in response to determining that the message recipientinformation for the particular message recipient indicates that messagesare not to be sent to the particular messaging recipient through theparticular messaging service. As shown within display screen 305 a, thewebsite associated with the corresponding message initiator 104 mayprompt the user of client device 102 to indicate whether they would liketo override their existing messaging preferences. The client device 102may, for example, display screen 305 b when the user of client device102 indicates whether they wish to override such existing messagingpreferences.

At 306, the client device 102 may provide confirmation of whether theuser of client device 102 wishes to override their existing messagingpreferences to the message initiator 104. This may, for instance, occurupon submission of user indication to the website associated with thecorresponding message initiator 104, as shown within display screen 305b. At 308, the message initiator 104 may provide a message request tothe messaging management service 120. Such a message request may besimilar to that which has been described above in association withmessage request 117, and may include a message content type identifierthat indicates a type of the message that is to be transmitted, dataidentifying the particular message recipient, and data indicating thatthe particular message recipient has overridden preference dataindicating that messages are not to be transmitted to the particularmessage recipient through the particular messaging service. Themessaging management service 120 may, for instance, respond to thismessage request in a manner similar to that which has been describedabove in association with FIGS. 1A and 1B. The messaging managementservice 120 may, however, temporarily disregard the information storedin preferences and contact details database 125 pertaining to thepreferences of the user of client device 102 with regard to theparticular messaging service based on the data indicating that theparticular message recipient has overridden preference data as includedin the message provided at 308 by the message initiator 104. Themessaging management service 120 may further rely upon such data toidentify the particular message template stored in template inventory123 that is formatted for the particular messaging service and thatcorresponds to the content type identifier provided in the message sentby the message initiator 104. The messaging management service 120 maythen proceed to retrieve the particular message template, generate amessage, and transmit the generated message to the particular messagingservice in a manner similar to that which has been described above inreference to FIGS. 1A and 1B. Following the example mentioned above, thegenerated message may, for instance, be that of a confirmation messagefor the purchase made by the user of client device 102 through thewebsite associated with message initiator 104.

FIG. 4 is a flowchart of an example process 400 for managing messages onbehalf of one or more message initiators. The following describes theprocess 400 as being performed by components of systems that aredescribed with reference to FIGS. 1A and 1B. However, process 400 may beperformed by other systems or system configurations.

The process 400 may include accessing, by a messaging managementservice, message recipient information that includes, for each ofmultiple message recipients, (i) preference data identifying one or moremessaging services through which messages are to be sent to the user,and, (ii) for each of the messaging services through which messages areto be sent to the user, account information for the user (402). Thismay, for instance, correspond to the messaging management service 120accessing or maintaining information stored in the preferences andcontact details database 125. The messaging services through whichrecipients may be provided messages may include social networkingservices, e-mail services, image sharing services, SMS or othertext-messaging services, mobile chat services, video conferencingservices, other messaging services that have yet to be released, and thelike.

The process 400 may include receiving, by the messaging managementservice and from a message initiator, a request to transmit a message,where the request includes at least (i) a message content typeidentifier that indicates a type of message that is to be transmitted,and (ii) data identifying one or more message recipients (404). Thismay, for instance, correspond to the messaging management service 120,in stage A, receiving message request 117 from a message initiator 104in response to the satisfaction of one or more conditions that aremonitored by the message initiator 104. In some examples, this requestmay further include (iii) a set of content that is to be included in themessage that is to be transmitted. The message request provided by themessage initiator 104 may further indicate that messages are to be sentto other recipients in addition to the user of client device 102. Insome implementations, the request to transmit the message may be sentfrom the message initiator and received by the messaging managementservice under a simple object access protocol (“SOAP”). In suchimplementations, the messaging management service may perform one ormore SOAP validation processes upon the request to transmit the messageand exchange data pertaining to results of the SOAP validation processeswith the message initiator.

The process 400 may include, for each message recipient, selecting, bythe messaging management service, one or more particular messagingservices based on the preference data for the message recipient (406).This may, for instance, correspond to the messaging management service120 identifying or selecting a particular subset of messaging service130 through which messages are to be sent to each recipient. In theexample of FIG. 1B, this may correspond to the messaging managementservice 120 identifying or selecting social networking service 130 a,e-mail service 130 b, and image sharing service 130 c from among themessaging services 130 that have been provisioned by messagingmanagement service 120.

The process 400 may include, for each particular messaging service,generating, by the messaging management service, a message based on themessage content type identifier (408). This may, for instance,correspond to the message generator 126 of messaging management service120 generating a message to provide to each selected messaging servicebased on a respective message template retrieved from template inventory125 based at least on message request 117. Messages for each particularmessaging service may, for example, be generated by a respectivesub-module included in the message generator 126.

In some implementations, generating the message based on the messagecontent type identifier may include selecting, from among multipletemplates that are each associated with different message content typeidentifiers, a particular template that is associated with the receivedmessage content type identifier, and populating the particular templatewith the set of content. In some examples, the multiple templates aremaintained by one or more administrators associated with the messageinitiator. This may, for instance, correspond to one or more usersassociated with the message initiator 104 interfacing with the messagingmanagement service 120 through the web administration console.

The process 400 may include, for each particular messaging service,transmitting, by the messaging management service, the message and theaccount information for the user to the messaging service (410). Thismay, for instance, correspond to the messaging management service 120providing a message 127 and account information 129 to each particularmessaging service in stage B. In the example of FIG. 1B, this maycorrespond to the messaging management service 120 providing messages127 a-c and account information 129 a-c to social networking service 130a, e-mail service 130 b, and image sharing service 130 c, respectively.The messaging management service 120 may perform such processes for eachof multiple recipients, for each of multiple message initiators.

In some implementations, the process 400 may further include, inresponse to transmitting the message, receiving, by the messagingmanagement service, an acknowledgement from the messaging service. Thismay, for instance, correspond to the messaging management service 120receiving one or more acknowledgements or negative-acknowledgments fromthe each one of messaging services 130 to which it has provided agenerated message in stage C.

In some implementations, the process 400 may further include generating,by the messaging management service, a response to the request based onat least one of the one or more acknowledgements, and transmitting, bythe messaging management service and to the message initiator, theresponse to the request. This may, for instance, correspond to themessaging management service 120 generating a response to messagerequest 117 based on the one or more acknowledgements it received instage D, and transmitting the response to message initiator 104 in stageE.

FIG. 5 is a schematic diagram of an example of a generic computer system500. The system 500 can be used for the operations described inassociation with FIGS. 1-4 according to some implementations. The system500 may be included in the system 100.

The system 500 includes a processor 510, a memory 520, a storage device530, and an input/output device 540. Each of the components 510, 520,530, and 540 are interconnected using a system bus 550. The processor510 is capable of processing instructions for execution within thesystem 500. In one implementation, the processor 510 is asingle-threaded processor. In another implementation, the processor 510is a multi-threaded processor. The processor 510 is capable ofprocessing instructions stored in the memory 520 or on the storagedevice 530 to display graphical information for a user interface on theinput/output device 540.

The memory 520 stores information within the system 500. In oneimplementation, the memory 520 is a computer-readable medium. In oneimplementation, the memory 520 is a volatile memory unit. In anotherimplementation, the memory 520 is a non-volatile memory unit.

The memory 520 stores information within the system 500. In oneimplementation, the memory 520 is a computer-readable medium. In oneimplementation, the memory 520 is a volatile memory unit. In anotherimplementation, the memory 520 is a non-volatile memory unit.

The storage device 530 is capable of providing mass storage for thesystem 500. In one implementation, the storage device 530 is acomputer-readable medium. In various different implementations, thestorage device 530 may be a floppy disk device, a hard disk device, anoptical disk device, or a tape device.

The input/output device 540 provides input/output operations for thesystem 500. In one implementation, the input/output device 540 includesa keyboard and/or pointing device. In another implementation, theinput/output device 540 includes a display unit for displaying graphicaluser interfaces.

The features described can be implemented in digital electroniccircuitry, or in computer hardware, firmware, software, or incombinations of them. The apparatus can be implemented in a computerprogram product tangibly embodied in an information carrier, e.g., in amachine-readable storage device, for execution by a programmableprocessor; and method steps can be performed by a programmable processorexecuting a program of instructions to perform functions of thedescribed implementations by operating on input data and generatingoutput. The described features can be implemented advantageously in oneor more computer programs that are executable on a programmable systemincluding at least one programmable processor coupled to receive dataand instructions from, and to transmit data and instructions to, a datastorage system, at least one input device, and at least one outputdevice. A computer program is a set of instructions that can be used,directly or indirectly, in a computer to perform a certain activity orbring about a certain result. A computer program can be written in anyform of programming language, including compiled or interpretedlanguages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment.

Suitable processors for the execution of a program of instructionsinclude, by way of example, both general and special purposemicroprocessors, and the sole processor or one of multiple processors ofany kind of computer. Generally, a processor will receive instructionsand data from a read-only memory or a random access memory or both. Theelements of a computer are a processor for executing instructions andone or more memories for storing instructions and data. Generally, acomputer will also include, or be operatively coupled to communicatewith, one or more mass storage devices for storing data files; suchdevices include magnetic disks, such as internal hard disks andremovable disks; magneto-optical disks; and optical disks. Storagedevices suitable for tangibly embodying computer program instructionsand data include all forms of non-volatile memory, including by way ofexample semiconductor memory devices, such as EPROM, EEPROM, and flashmemory devices; magnetic disks such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks. Theprocessor and the memory can be supplemented by, or incorporated in,ASICs (application-specific integrated circuits).

To provide for interaction with a user, the features can be implementedon a computer having a display device such as a CRT (cathode ray tube)or LCD (liquid crystal display) monitor for displaying information tothe user and a keyboard and a pointing device such as a mouse or atrackball by which the user can provide input to the computer.

The features can be implemented in a computer system that includes aback-end component, such as a data server, or that includes a middlewarecomponent, such as an application server or an Internet server, or thatincludes a front-end component, such as a client computer having agraphical user interface or an Internet browser, or any combination ofthem. The components of the system can be connected by any form ormedium of digital data communication such as a communication network.Examples of communication networks include, e.g., a LAN, a WAN, and thecomputers and networks forming the Internet.

The computer system can include clients and servers. A client and serverare generally remote from each other and typically interact through anetwork, such as the described one. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. Accordingly, otherimplementations are within the scope of the following claims.

What is claimed is:
 1. A computer-implemented method comprising:accessing, by a messaging management service, message recipientinformation that includes, for each of multiple message recipients, (i)preference data identifying one or more existing messaging servicesthrough which messages are to be sent to a user, and, (ii) for each ofthe existing messaging services through which messages are to be sent tothe user, account information for the user; receiving, by the messagingmanagement service, new messaging service provisioning information for anew messaging service, wherein the new messaging service provisioninginformation includes (i) information that associates message contenttype identifiers to message templates that are formatted for themessaging service, and (ii) instructions for electronicallycommunicating messages to the new messaging service; transmitting, bythe messaging management service and to one or more message initiators,a notification indicating that messages may now be transmitted throughthe new messaging service; and receiving, by the messaging managementservice and from one or more of the message initiators, updated messagerecipient information that includes, for each of one or more of themultiple message recipients, (i) updated preference data identifying thenew messaging service, and, (ii) account information for the newmessaging service and the user.
 2. The computer-implemented method ofclaim 1, wherein receiving, by the messaging management service and fromone or more of the message initiators, updated message recipientinformation comprises: receiving, by the messaging management serviceand from one or more of the message initiators, updated messagerecipient information based on an indication that the user would likereceive messages through the new messaging service.
 3. Thecomputer-implemented method of claim 2, wherein the indication that theuser would like receive messages through the new messaging service isreceived by the message initiator through a website associated with themessage initiator.
 4. The computer-implemented method of claim 1,further comprising: receiving, by the messaging management service, oneor more updates to enable the messaging management service to generatemessages that are compatible with the new messaging service.
 5. Thecomputer-implemented method of claim 1, further comprising: updating themessage recipient information for each of the one or more of themultiple message recipients, to reflect the (i) updated preference dataidentifying the new messaging service, and, (ii) account information forthe new messaging service and the user.
 6. The computer-implementedmethod of claim 1, wherein the existing messaging services include oneor more social networking services.
 7. The computer-implemented methodof claim 1, wherein the preference data further identifies a language inwhich messages are to be provided to the user.
 8. A system comprising:one or more computers and one or more storage devices storinginstructions that are operable, when executed by the one or morecomputers, to cause the one or more computers to perform operationscomprising: accessing, by a messaging management service, messagerecipient information that includes, for each of multiple messagerecipients, (i) preference data identifying one or more existingmessaging services through which messages are to be sent to a user, and,(ii) for each of the existing messaging services through which messagesare to be sent to the user, account information for the user; receiving,by the messaging management service, new messaging service provisioninginformation for a new messaging service, wherein the new messagingservice provisioning information includes (i) information thatassociates message content type identifiers to message templates thatare formatted for the messaging service, and (ii) instructions forelectronically communicating messages to the new messaging service;transmitting, by the messaging management service and to one or moremessage initiators, a notification indicating that messages may now betransmitted through the new messaging service; and receiving, by themessaging management service and from one or more of the messageinitiators, updated message recipient information that includes, foreach of one or more of the multiple message recipients, (i) updatedpreference data identifying the new messaging service, and, (ii) accountinformation for the new messaging service and the user.
 9. The system ofclaim 8, wherein receiving, by the messaging management service and fromone or more of the message initiators, updated message recipientinformation comprises: receiving, by the messaging management serviceand from one or more of the message initiators, updated messagerecipient information based on an indication that the user would likereceive messages through the new messaging service.
 10. The system ofclaim 9, wherein the indication that the user would like receivemessages through the new messaging service is received by the messageinitiator through a website associated with the message initiator. 11.The system of claim 8, the operations further comprising: receiving, bythe messaging management service, one or more updates to enable themessaging management service to generate messages that are compatiblewith the new messaging service.
 12. The system of claim 8, theoperations further comprising: updating the message recipientinformation for each of the one or more of the multiple messagerecipients, to reflect the (i) updated preference data identifying thenew messaging service, and, (ii) account information for the newmessaging service and the user.
 13. The system of claim 8, wherein theexisting messaging services include one or more social networkingservices.
 14. The system of claim 8, wherein the preference data furtheridentifies a language in which messages are to be provided to the user.15. A non-transitory computer-readable medium storing softwarecomprising instructions executable by one or more computers which, uponsuch execution, cause the one or more computers to perform operationscomprising: accessing, by a messaging management service, messagerecipient information that includes, for each of multiple messagerecipients, (i) preference data identifying one or more existingmessaging services through which messages are to be sent to a user, and,(ii) for each of the existing messaging services through which messagesare to be sent to the user, account information for the user; receiving,by the messaging management service, new messaging service provisioninginformation for a new messaging service, wherein the new messagingservice provisioning information includes (i) information thatassociates message content type identifiers to message templates thatare formatted for the messaging service, and (ii) instructions forelectronically communicating messages to the new messaging service;transmitting, by the messaging management service and to one or moremessage initiators, a notification indicating that messages may now betransmitted through the new messaging service; and receiving, by themessaging management service and from one or more of the messageinitiators, updated message recipient information that includes, foreach of one or more of the multiple message recipients, (i) updatedpreference data identifying the new messaging service, and, (ii) accountinformation for the new messaging service and the user.
 16. The mediumof claim 15, wherein receiving, by the messaging management service andfrom one or more of the message initiators, updated message recipientinformation comprises: receiving, by the messaging management serviceand from one or more of the message initiators, updated messagerecipient information based on an indication that the user would likereceive messages through the new messaging service.
 17. The medium ofclaim 16, wherein the indication that the user would like receivemessages through the new messaging service is received by the messageinitiator through a website associated with the message initiator. 18.The medium of claim 15, the operations further comprising: receiving, bythe messaging management service, one or more updates to enable themessaging management service to generate messages that are compatiblewith the new messaging service.
 19. The medium of claim 15, theoperations further comprising: updating the message recipientinformation for each of the one or more of the multiple messagerecipients, to reflect the (i) updated preference data identifying thenew messaging service, and, (ii) account information for the newmessaging service and the user.
 20. The medium of claim 15, wherein theexisting messaging services include one or more social networkingservices.